Rights expression profile system and method using templates

ABSTRACT

A system and method for creating a rights expression for association with an item for use in a system for controlling use of the item in accordance with the rights expression, including specifying rights expression information indicating a manner of use of an item, the rights expression information including at least one element, the element having a variable and corresponding value for the variable; and performing an encoding process, including determining an identifier associated with a template corresponding to the rights expression information, extracting from the rights expression information the value for the variable corresponding to the element, and encoding a license adapted to be enforced on a device based on the variable and the identifier, the license including an identification of the template and the value for the variable.

CROSS REFERENCE TO RELATED DOCUMENTS

The present invention claims benefit of priority under 35 U.S.C. §119(e) to commonly assigned, U.S. Provisional Patent Application Ser. No. 60/363,932 of Raley et al., entitled “USE OF RIGHTS EXPRESSIONS IN APPLICATIONS WITH PERFORMANCE CONSTRAINTS,” filed on Mar. 14, 2002, the entire disclosure of which is hereby incorporated by reference herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention generally relates to controlling use of content, or other items, through rights expressions associated with the content or other items, and more particularly to a system and method for generating templates of rights expressions.

2. Description of Related Art

One of the most important issues concerning the widespread distribution of digital content, such as documents, music, movies, software, information, and the like, in forms usable by computing devices, via electronic means, and the Internet in particular, is the provision of the ability to enforce the intellectual property rights during the distribution and use of the digital content. Technologies for resolving this problem are referred to as Digital Rights Management (DRM) herein. However, there are a number of issues to be considered in effecting a DRM system, such as authentication, authorization, accounting, payment and financial clearing, rights specification, rights verification, rights enforcement, and document protection issues, to name but a few.

For example, in the world of printed documents and other physical content, a work created by an author is usually provided to a publisher, which formats and prints numerous copies of the work. The copies are then sent by a distributor to bookstores or other retail outlets, from which the copies are purchased by end users. While the low quality of copying and the high cost of distributing printed material have served as deterrents to unauthorized copying of most printed documents, it is much easier to copy, modify, and redistribute unprotected digital content with high quality. Therefore, there is a need for mechanisms to protect digital content.

Difficulties associated with preventing, or even deterring, people from making unauthorized copies of electronic content within current general-purpose computing and communications systems, such as personal computers, workstations, and other devices connected over communications networks, such as local area networks (LANs), intranets, and the Internet, are widely recognized. Many attempts to provide hardware-based solutions to prevent unauthorized copying have proven to be unsuccessful. Moreover, the deployment of high bandwidth or broadband communications technologies and the development of what is presently known as the National Information Infrastructure (NII) is making it more convenient to distribute large documents electronically, including video files, such as full length motion pictures, and this makes it easier to proliferate unauthorized copying and distribution of digital content. Therefore, the need for further development of DRM technologies is becoming a high priority.

Accordingly, commonly-assigned U.S. Pat. No. 5,634,012 discloses a DRM system for controlling the distribution of digital content, wherein devices of the DRM system can include a repository associated therewith. A predetermined set of usage transaction steps define a protocol used by the repositories for enforcing usage rights associated with the content. Usage rights persist with the content and the usage rights associated with the content comprise a digital work. The usage rights can permit various manners of use of the content, such as a right to view or print or display the content, a right to use the content only once, a right to distribute or redistribute the content, and the like. Such usage rights can be made contingent on payment or other conditions. However, there is still a further need for systems and methods for expressing and enforcing usage rights and/or conditions associated with content in a flexible and robust manner.

SUMMARY OF THE INVENTION

The above and other needs are addressed by embodiments of the present invention, which provide an improved system and method for expressing usage rights for content or other items based on modulated or varied signals or graphical representations of the usage rights.

According, in one aspect of an embodiment of the present invention, there is provided a system and method for creating a rights expression for association with an item for use in a system for controlling use of the item in accordance with the rights expression, including specifying rights expression information indicating a manner of use of an item, the rights expression information including at least one element, the element having a variable and corresponding value for the variable; and performing an encoding process, including determining an identifier associated with a template corresponding to the rights expression information, extracting from the rights expression information the value for the variable corresponding to the element, and encoding a license adapted to be enforced on a device based on the variable and the identifier, the license including an identification of the template and the value for the variable.

Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, simply by illustrating a number of exemplary embodiments and implementations, including the best mode contemplated for carrying out the present invention. The present invention is also capable of other and different embodiments, and its several details can be modified in various respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:

FIG. 1 illustrates an exemplary Digital Rights Management system on which various embodiments of the present invention can be implemented;

FIG. 2 is a flowchart illustrating an exemplary rights expression profiling process;

FIG. 3 illustrates an exemplary rights expression encoding and decoding sub-system for resource-constrained devices in the Digital Rights Management system of FIG. 1;

FIG. 4 is a flowchart illustrating the exemplary rights expression encoding and decoding process of FIG. 3;

FIG. 5 illustrates an exemplary rights expression template mapping sub-system in the Digital Rights Management system of FIG. 1;

FIG. 6 is a flowchart illustrating exemplary template mapping processes of the sub-system of FIG. 5;

FIG. 7 further illustrates the exemplary rights expression encoding and decoding sub-system FIG. 3 based on a license signature value;

FIG. 8 further illustrates the exemplary rights expression encoding and decoding sub-system FIG. 3 based a signature value for license variables;

FIG. 9 illustrates an exemplary templatespace for resource-constrained devices in the Digital Rights Management system of FIG. 1; and

FIG. 10 illustrates an exemplary symbolic representation of a rights expression including a profile or template that can be generated by the Digital Rights Management system of FIG. 1.

DETAILED DESCRIPTION OF THE INVENTION

A system and method for profiling rights expressions are described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It is apparent to one skilled in the art, however, that the present invention can be practiced without these specific details or with equivalent arrangements. In some instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention.

As noted above, authentication, authorization, accounting, payment and financial clearing, rights specification, rights verification, rights enforcement, and document protection issues should be addressed by a Digital Rights Management system. Commonly-assigned U.S. Pat. No. 5,530,235, U.S. Pat. No. 5,629,980, U.S. Pat. No. 5,634,012, U.S. Pat. No. 5,638,443, U.S. Pat. No. 5,715,403, U.S. Pat. No. 6,233,684, and U.S. Pat. No. 6,236,971, the entire disclosures of all of which are hereby incorporated by reference herein, disclose DRM systems addressing these and other issues.

A human-readable, machine-readable rights expression language, such as XrML or an XML-based language, can be used to express a rights expression. Advantageously, a rights expression, such as a license, can express a usage right specifying a permitted manner of use of an item, such as digital content, services. However, many digital content consumption devices, for example, resource-constrained devices, such as MP3 players, mobile phones, handheld device, PDAs, set-top boxes, and Internet appliances can have limited storage capabilities, and processing capabilities. Accordingly, it can be difficult for such devices to include full-featured rights expression interpreters, such as XrML interpreters or XML interpreters, for processing rights expressions.

The present invention includes recognition that resource-constrained devices can benefit from employing a rights expression, for example, to consume digital content. However, the associated rights expression parsing tools, transport mechanisms, and encoding mechanisms can prove taxing for such devices, resulting in less than optimal consumption of the digital content.

Therefore, there exists a need for optimizing rights expressions, the resources employed to interpret rights expressions, so that resource-constrained devices can enjoy the full benefit of employing rights expressions in an efficient and robust manner. The exemplary embodiments, as described herein, address the above and other problems by providing exemplary techniques based on exemplary profiles, and templates.

Referring now to the drawings, wherein like reference numerals designate identical or corresponding parts throughout the several views, and more particularly to FIG. 1 thereof, there is illustrated a Digital Rights Management system 100 that can be used in connection with the described exemplary embodiments to specify and enforce usage rights for content, services, or other property. In FIG. 1, the Digital Rights Management system 100 includes a user activation component in the form of an activation server 110 that issues a set of public and private key pairs 112 to a content user in a protected fashion. Typically, when the user uses the Digital Rights Management system 100 for the first time, the user installs software that, for example, works with, or includes, a rendering application for a particular content format.

The software is installed in a client environment 120, for example, such as a computing device associated with the user. The software can be part of the Digital Rights Management system 100 and can be used to access protected content 134. After the installation, the software can be activated. During the activation process, some information is exchanged between the activation server 110 and the client environment 120. A client software component 122 can be downloaded and installed in the client environment 120. The client software component 122 can be tamper resistant and can include the set of public and private key pairs 112 issued by the activation server 110, as well as other components.

A rights offer 132 can be associated with the protected content 134 and can specify usage rights 132A that are available to an end-user, for example, when one or more corresponding conditions 132B are satisfied. A license server 140 manages the encryption keys 112 and issues a license 142 for the protected content 134. The license 142 can embody the actual granting of the usage rights 132A to the end user. For example, the rights offer 132 may grant the end user the right to view the protected content 134 on the condition of payment of a fee of five dollars, and the right to print the protected content on the condition of payment of a fee of ten dollars. The license 142 can be issued for the view right when the five dollar fee has been paid and/or for the print right when 10 dollar fee has been paid. The client component 122 interprets and enforces the rights that have been specified in the license 142.

Clear content 136, such as unprotected content, and the like, can be prepared, for example, with an application 138, such as a document preparation application, installed on a computer 130 associated with a content publisher, a content distributor, a content service provider, or any other suitable party. Preparation of the clear content 136 can include specifying the usage rights 132A and the conditions 132B under which the clear content 136 can be used, associating the rights offer 132 with the clear content 136, and protecting the clear content 136 with, for example, a cryptography algorithm to generate the protected content 134. A rights language, such as XrML, eXtensible Access Control Markup Language (XACML), Open Digital Rights Language (ODRL), and the like, can be used to specify the rights offer 132. However, the rights offer 132 can be specified in any suitable manner. Note the phrase “specifying rights information”, as used herein, refers to creating, deriving, or other wise utilizing information that relates to rights expressions. Also, the rights offer 132 can be in the form of a pre-defined specification, profile, template, and the like, that can be associated with the protected content 134. Accordingly, the process of specifying the rights offer 132 can include any suitable process for associating rights, conditions, and the like, with content. The rights offer 132 associated with the protected content 134 and the encryption key 112 used to encrypt the clear content 136 can be transmitted to the license server 140.

A typical workflow for the Digital Rights Management system 100 can include a user operating within the client environment 120 being activated for receiving the protected content 134 by the activation server 110. The activation process results in the public and private key pair 112, and, for example, some user and/or machine-specific information, and the like, being downloaded to the client environment 120 in the form of the client software component 122. The activation process can be accomplished, for example, at any suitable time prior to the issuing of the license 142.

When the user wishes to use the protected content 134, the user makes a request for the protected content 134. For example, the user might browse a Web site running on a Web server 150, using a browser installed in the client environment 120, and attempt to download the protected content 134. During this process, the user may go through a series of steps possibly including a fee transaction, such as in the sale of content, other transactions, such as collection of information, and the like. When the appropriate conditions and other prerequisites, such as the collection of a fee and verification that the user has been activated, are satisfied, the Web server 150 contacts the license server 140, for example, through a secure communications channel, such as a channel using a Secure Sockets Layer (SSL). The license server 140 then generates the license 142 for the protected content 134 and the Web server 150 downloads both the protected content 134 and the license 142. The license 142 can include the appropriate usage rights of the usage rights 132A and can be downloaded from the license server 140 or an associated device. The protected content 134 can be downloaded from the computer 130 associated with a publisher, distributor, or other party. The rights offer 132 can be persistent and remain associated with the protected content 134.

The client software component 122 in the client environment 120 can then proceed to interpret the license 142 and allow use of the protected content 134 based on the rights 132A and the conditions 132B specified in the license 142. The interpretation and enforcement of the usage rights, for example, are further described in commonly-assigned U.S. Pat. No. 5,530,235, No. 5,629,980, No. 5,634,012, No. 5,638,443, No. 5,715,403, No. 6,233,684, and No. 6,236,971. The above steps can take place sequentially, approximately simultaneously, in various orders, and the like.

The Digital Rights Management system 100 addresses security aspects of protecting the protected content 134. In particular, the Digital Rights Management system 100 can authenticate the license 142 that has been issued by the license server 140. One way to accomplish such authentication is for the client software component 122 to determine if the licenses 142 can be trusted. In other words, the client software component 122 can include the capability to verify and/or validate the cryptographic signature, or other identifying characteristic of the license 142. During the activation step described above, the client environment 120 and the license server 140 can receive the set of keys 112, for example, in a tamper-resistant software package that can include other components, such as the client software component 122 for the activated client environment 120 to verify the signature of the license 142.

The Digital Rights Management system 100 is of an exemplary nature and can be implemented in numerous other equivalent arrangements. For example, the license 142 and the protected content 134 can be distributed from different entities. As another example, the rights offer 132 can be associated with the protected content 134 by a party other than the party preparing the protected content 134. As a further example, a clearinghouse 160 can be used to process payment transactions and verify payment prior to issuing the license 142. Moreover, the various processes and transactions can be performed, for example, via online and/or offline environments and/or combinations thereof. For example, an end user could download content to a computer and then transfer the content from the computer to a personal digital assistant (PDA). The end user could then buy a license for the content, for example, via a supermarket kiosk, a cash register, a prep-paid license card, and the like, and then transfer the license to the PDA. The end user could then activate the content for use on the PDA and/or the computer. In such an offline scenario, the various devices can, but need not, communicate directly with one another and information can be exchanged in any suitable manner, such as by physically moving media between the devices.

The exemplary profiles and templates, as described herein, can be employed to compress the size of a rights expression, such as an XrML rights expression, and the like. Advantageously, the exemplary profiles and templates can be employed for minimizing the amount of processing resources employed for interpreting a rights expression by a resource-constrained application, device, system, platform, and the like.

According to an exemplary embodiment, if X can be considered to be the set of all conformant expressions of a rights expression language, then a rights expression language profile can be defined as some non-empty subset Y of X. If a given expression E can be an element of Y, then E can be said to be in the profile. However, if E is not an element of Y, then E can be said to be invalid against the profile. Thus, according to an exemplary embodiment, profiling of a rights expression language can include identifying subsets of the rights expression language that a particular interpreter can support, and interpret. Advantageously, profiling can be employed for allowing resource-constrained devices to participate in a rights-interpreted language system.

According to the exemplary embodiments, there are numerous forms of and ways to create rights expression language profiles, such as by employing mechanisms based templates. Techniques associated with templates, for example, mapping of templates to objects, such as binary tokens, can be referred to as template mapping to describe the collection of such technologies.

The exemplary template mapping and profiling techniques compress the size of a rights expression. For example, the best compression that can be achieved for a rights expression language can be to identify all distinct rights expressions that can exist within a given domain, and assign each and every rights expression a reference value. In this way, a rights expression language interpreter would only need to lookup a given rights expression by the reference value in order to interpret the corresponding rights expression. The exemplary template mapping and profiling techniques attempt to reach such a level of compression via exemplary template, and profile encoding, and decoding processes.

An exemplary encoding process can include removing one or more values for variable fields from a rights expression to generate a template or profile for the rights expression, and assigning an identifier (id) to the template or profile. Advantageously, the identifier can be transmitted along with the one or more values for the variable fields of the rights expression, for example, to a resource-constrained device, instead of transmitting the entire or raw rights expression.

An exemplary decoding process can include receiving the identifier and the one or more values for the variable fields, and interpreting the rights expression, based on the transmitted values, for example, on a resource-constrained device. Advantageously, such an interpreter can include minimal computing resources, instead of a full rights expression language parser that would be employed to interpret the entire or raw rights expression.

In addition, the exemplary encoding, and decoding techniques, advantageously, can provide lossless compression, and decompression. For example, an original rights expression can be generated, recreated, reconstructed or copied, by populating one or more values for the variable fields from the original rights expression into a template or profile corresponding to the original rights expression, as identified by a corresponding identifier. High-end rights management applications, devices, and systems can employ the reconstructed rights expression, advantageously, providing interoperability with resource-constrained devices.

The following exemplary namespace table, as shown in Table 1 below, illustrates the exemplary template mapping and profiling techniques, as applied to exemplary rights expressions in the form of exemplary XrML licenses related to music, and audio. The XrML Specification can be obtained on the World Wide Web (www) at xrml.org. In addition, a Sample Extension Schema (schema/2001/11/compactMusic) is provided as an Appendix herewith.

TABLE 1 Namespaces Table Prefix Namespace Schema Description (r) http://www.xrml.org/schema/2001/11/xrml2core XrML 2.0 Core Sx http://www.xrml.org/schema/2001/11/xrml2sx Standard Extension Cx http://www.xrml.org/schema/2001/11/xrml2cx Content Extension Cm http://www.xrml.org/schema/2001/11/xrml2compactMusic Sample Extension Dsig http://www.w3.org/2000/09/xmldsig# Digital Signature Xsi http://www.w3.org/2001/XMLSchema-instance Schema Instance

A rights expression in the form of an XrML license issued by an identified device, can be used specify that a device identified in the license can play an identified song file, as expressed in the following first exemplary license (L1).

First Exemplary License (L1):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

With the exemplary license L1, it can be assumed that: (i) license redistribution is not an employed business model, (ii) the employed device can use any suitable song file input mechanism, (iii) the employed device can play the song file, (iv) security is not a concern, as the employed device can be identified by a an identification number, the song file can be identified by an identification number, and the exemplary license L1 identifies the issuing device, without employing a signature, (v) the exemplary license L1 can travel with the song file, so that no searching for the exemplary license L1 is necessary, and (vi) no Internet access is available to the employed device. According to the exemplary license L1, a device with identification number 123 can be granted a usage right to play a song file having identification number 456 an unlimited number of times, according to an issuing device with identification number 024. Additional flexibility can be employed by specifying in a license a limit on the number of times that the device 123 can play the song file 465, as expressed in the following second exemplary license (L2).

Second Exemplary License (L2):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>   <sx:exerciseLimit>    <sx:stateReference>     <cm:countKeeper key=“789”/>      <cm:device cmid=“123”/>     </cm:countKeeper>    </sx:stateReference>   </sx:exerciseLimit>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

Accordingly, the exemplary license L2 can be similar to the exemplary license L1, except for bolded portion, which can specify that there can be a limit on the number of times the song file 456 can be played by the device 123, and that the remaining number of times the song file 456 can be played must be counted and stored on the device 123, with a lookup key 789. A license, however, can be employed to allow unlimited license redistribution to identified devices, as expressed in the following third exemplary license (L3).

Third Exemplary License (L3):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <grant>   <cm:device cmid=“123”/>   <issue/>   <grant>    <cm:device cmid=“111”/>    <cx:play/>    <cm:song cmid=“456”/>   </grant>  </grant>  <grant>   <cm:device cmid=“123”/>   <issue/>   <grant>    <cm:device cmid=“333”/>    <cx:play/>    <cm:song cmid=“456”/>   </grant>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L3 can be similar to the exemplary license L1, except for the bolded portion, which can identify the devices as 111 and 333 to which the song file 456 can be redistributed. Accordingly, with the exemplary license L3, the device 123 has the right to issue grants to the devices 111 and 333 to play the song file 456. Advantageously, the devices 111 and 333 do not have to be as sophisticated as the device 123, as the issued licenses would look nearly identical to the exemplary license L1, differing only in the device identifications. A license, however, can allow limited license redistribution to unidentified devices, as expressed in the following fourth exemplary license (L4).

Fourth Exemplary License (L4):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <grant>   <forAll varName=“otherDevice”/>   <cm:device cmid=“123”/>   <issue/>   <grant>    <cm:device varRef=“otherDevice”/>    <cx:play/>    <cm:song cmid=“456”/>   </grant>   <sx:exerciseLimit>    <sx:stateReference>     <cm:countKeeper key=“555”>      <cm:device cmid=“123”/>     </cm:countKeeper>    </sx:stateReference>   </sx:exerciseLimit>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L4 can be similar to the exemplary license L3, except for the bolded portion, which can be used allow or require the device 123 to selectively distribute a license to play the song file 456 to unidentified devices, a limited number of times, with the number of times remaining stored on the device 123 under lookup key 555. Advantageously, the devices to which the device 123 issues the licenses do not have to be as sophisticated as the device 123, as the issued licenses would look nearly identical to the exemplary license L1, differing only in the device identifications.

A license also can specify the playing of an identified song file, on an identified device, to be restricted to a fixed time interval, as expressed in the following fifth exemplary license (L5).

Fifth Exemplary License (L5):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>   <validityInterval>    <notBefore>2002-03-04T05:06:07</notBefore>    <notAfter>2002-03-11T05:06:07</notAfter>   </validityInterval>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L5 can be similar to the exemplary license L1, except for the bolded portion, which can be used specify that the device 123 can be restricted to playing the song file 456 during the specified time interval. The playing of an identified song file, on an identified device, also can be restricted to a fixed time interval that can start the first time the song file can be played, as expressed in the following sixth exemplary license (L6).

Sixth Exemplary License (L6):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>   <sx:validityIntervalFloating>    <sx:stateReference>     <cm:intervalKeeper key=“777”>      <cm:device cmid=“123”/>     </cm:intervalKeeper>    </sx:stateReference>   </sx:validityIntervalFloating>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L6 can be similar to the exemplary license L1, except for the bolded portion, which can be used specify that the device 123 can be restricted to playing the song file 456 from the first time the song file 456 is played, wherein the time remaining and the start time can be stored by the device 123 under lookup key 777. In a further example, a license can be employed to allow the lending by an identified device of an identified song file to up to a predetermined number of other devices, as expressed in the following seventh exemplary license (L7).

Seventh Exemplary License (L7):

<license>  <grant>   <cm:device cmid=“123”/>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <grant>   <forAll varName=“otherDevice”/>   <forAll varName=“interval”/>   <cm:device cmid=“123”/>   <issue/>   <grant>    <cm:device varRef=“otherDevice”/>    <cx:play/>    <cm:song cmid=“456”/>    <validityInterval varRef=“interval”/>   </grant>   <cm:copyManagement>    <sx:stateReference>     <cm:copyKeeper key=“999”>      <cm:device cmid=“123”/>     </cm:copyKeeper>     <serviceParameters>      <datum>       <validityInterval        varRef=“interval”/>      </datum>     </serviceParameters>    </sx:stateReference>   </cm:copyManagement>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L7 can be similar to the exemplary license L4, except for the bolded portion, which can specify a variable time constraint, a copy management constraint. For example, a literal rendering of the bolded portion can be that “the device 123 can choose a device and an interval and can then issue a license allowing the chosen device to play the song file 456 during the chosen interval if the device 123 passes the chosen interval to a copy keeper using a lookup key 999 on the device 123 and the copy keeper verifies that there are still copies remaining for the chosen interval.”

Advantageously, the devices to which the device 123 lends the song file 456 do not have to be as sophisticated as the device 123, as the issued licenses would look nearly identical to the exemplary license L5, differing only in the device identifications and the validity interval. By contrast, a song could specified to be played an unlimited number of times, as expressed in the following eighth exemplary license (L8).

Eight Exemplary License (L8):

<license>  <grant>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L8 can be similar to the exemplary license L1, except for the omission of the identified device 123. Advantageously, any suitable device can play the song file 456 with the exemplary license L8, whereas with the next example, multiple devices within a same domain can play an identified song file, as expressed in the following ninth exemplary license (L9).

Ninth Exemplary License (L9):

<license>  <grant>   <forAll varName=“device”>    <everyone>     <cm:myDomain/>     <trustedIssuer>      <cm:device cmid=“000”/>     </trustedIssuer>    </everyone>   </forAll>   <cm:device varRef=“device”/>   <cx:play/>   <cm:song cmid=“456”/>  </grant>  <cm:issuerDevice>   <cm:device cmid=“024”/>  </cm:issuerDevice> </license>

The exemplary license L9 can be similar to the exemplary license L1, except for the bolded portion, which can be read as “every device that device 000 says can be in its domain can play the song file 456,” and the like. Advantageously, a license can be employed to provide a way for the device 000 to specify that some other device can be in its domain, as expressed in the following tenth exemplary license (L10).

Tenth Exemplary License (L10):

<license>  <grant>   <cm:device cmid=“123”/>   <possessProperty/>   <cm:myDomain/>   <validityInterval>    <notBefore>2002-03-01T00:00:00</notBefore>    <notAfter>2002-03-15T00:00:00</notAfter>   </validityInterval>  </grant>  <cm:issuerDevice>   <cm:device cmid=“000”/>  </cm:issuerDevice> </license>

The exemplary license L10 can be similar to the exemplary license L1, except for the bolded portion, wherein the issuer can be device 000, which can certify that the device 123 is in the domain of the device 000 during a specified time interval. For example, the device 123, such as an MP3 player can play the song file 456 during the specified time interval, if the device 000, such as a personal computer can certify that the device 123 is within the domain, such as on the same network of the device 000 during the specified time interval. Advantageously, if the device 123 received the exemplary license L10 from the device 000 during the specified time interval, the device 123 would know that the device 123 could play the song file 456. The exemplary license L9 would probably arrive at the device 123 along with the song file 456. The exemplary license L10, however, would probably arrive via some other means. For example, every time device 123 connects to a home network in device 000 domain, device 000 might send a new or updated exemplary license L10 to the device 123.

The final example is directed to a license enabling the secure identification of entities, so that a security model or trust policy can be put in place, for example, as expressed in the following eleventh exemplary license (L11).

Eleventh Exemplary License (L11):

<license>  <grant>   <keyHolder>    <info>     <dsig:KeyValue>      <dsig:RSAKeyValue>       <dsig:Modulus>oRUTUiTQkM.........</dsig:Modulus>       <dsig:Exponent>AQABAA==</dsig:Exponent>      </dsig:RSAKeyValue>     </dsig:KeyValue>    </info>   </keyHolder>   <cx:play/>   <digitalResource>    <secureIndirect URI=“http://www.xrml.org/.../songs/456”>      <dsig:DigestMethod Algorithm=      “http://.../xmldsig#sha1”/>     <dsig:DigestValue>PB4QbKOQCo941tTExbj1/Q==     dsig:DigestValue>    </secureIndirect>   </digitalResource>   <sx:exerciseLimit>    <sx:stateReference>     <uddi>      <serviceKey>       <uuid>D04951E4-332C-4693-B7DB-       D3D1D1C20844</uuid>      </serviceKey>     </uddi>    </sx:stateReference>   </sx:exerciseLimit>  </grant>  <issuer>   <dsig:Signature>    <dsig:SignedInfo>     <dsig:C...14...NMethod Algorithm=     “http:.../REC-xml-c14n-20010315”/>     <dsig:SignatureMethod Algorithm=     “http://.../xmldsig#rsa-sha1”/>     <dsig:Reference>      <dsig:Transforms>       <dsig:Transform Algorithm=       “http://.../xrml2core#license”/>      </dsig:Transforms>      <dsig:DigestMethod Algorithm=      “http://.../xmldsig#sha1”/>      <dsig:DigestValue>PB4QbKOQCo941tTEx...      </dsig:DigestValue>     </dsig:Reference>    </dsig:SignedInfo>    <dsig:SignatureValue>AYmqOhSHbiP9JadD2...    </dsig:SignatureValue>    <dsig:KeyInfo>     <dsig:KeyValue>      <dsig:RSAKeyValue>       <dsig:Modulus>X0j9q9OAxvhre4NP6q...       </dsig:Modulus>       <dsig:Exponent>AQABAA==</dsig:Exponent>      </dsig:RSAKeyValue>     </dsig:KeyValue>    </dsig:KeyInfo>   </dsig:Signature>  </issuer> </license>

The exemplary license L11 can be similar to the exemplary license L2, except for the first through fourth bolded portions, wherein the device identifier 123 can be replaced with a public key identification of the device 123, the song file 456 can be replaced with a cryptographically secure reference to the song file 456 via a hash value, the lookup key 789 on the device 123 can be replaced with a Universal Description, Discovery and Integration (UDDI) service key of an online counter service, the issuer device 024 can be replaced with a public key identification of the issuer and the issuer's signature of the exemplary license L11.

Advantageously, efficient exemplary profiles can be constructed based on the exemplary licenses L1-L11. An exemplary profile, based on the exemplary license L1, referred to as profile B, can be constructed, generated, and the like. A license can be in the exemplary profile B, for example, if the license can be similar the exemplary license L1, with the possible exception of having different cmid values.

For example, the exemplary license L3 would not be in the exemplary profile B, because of the additional cmid values 111 and 333 included in the exemplary license L3, which could not be included in the exemplary profile B. However, a license that the device 123 can issue to devices 111 or 333, for example, pursuant to the exemplary unlimited redistribution license L3, and the like, can be in the exemplary profile B. In this case, the license issued by the device 123 would be similar to the exemplary license L1, except that the issuer device would change from 024 to 123, the playing device 123 would be changed 111 or 333, and the like. Also, trivially, the exemplary license L1 can be in the exemplary profile B.

In a similar manner, an exemplary profile, based on the exemplary license L2, referred to as profile C, can be constructed, generated, and the like. A license can be in the exemplary profile C, for example, if (i) the license can be similar to the exemplary license L2, for example, with the possible exception of having different cmid values corresponding to the cmid values 123, 456, and 024 of the exemplary license L2, (ii) the cmid value of the device on which the count can be kept can be the same as the cmid value of the device that can exercise the right to play the identified song file, and the like.

FIG. 2 is a flowchart illustrating an exemplary rights expression profiling process. In FIG. 2, at step 201, for example, the profiling process can include obtaining a license. At step 203, for example, the license can be compared against a profile. At step 205, for example, it is determined whether or not the license is in the profile by comparing the license and the profile to determine if the license and the profile are similar except for having different values for one or more corresponding variable values. If the license is determined to be the profile at step 205, the license can be classified as being in the profile at step 207. Otherwise the license can be classified as being invalid against the profile at step 209.

Advantageously, profiling can allow devices, for example, to easily classify their capabilities, and the like. For example, a device that only supports profile B would not support limits related the exercise of the right to play the identified song file, and the like. By contrast, a device that supports profile C could support exercise limits, but only if the state can be kept on the same device.

Profiling, and template mapping can be employed, advantageously, for compression of a rights expression, as illustrated in an exemplary byte table shown in Table 2.

TABLE 2 Exemplary Byte Table. Meaning Bytes Value Compression Algorithm 0 0x00 Reserved 0x01 Algorithm B for Profile B 0x02 Algorithm C for Profile C 0x03–0xFE Future Algorithms 0xFF Uncompressed 1 − 3 Size of (un)compressed data 4 through x + 3 (Un)compressed data

As shown in Table 2, for example, byte 0 can be used for storing information, such as identification numbers for employed algorithms, profiles, or templates, bytes 1-3 can be used for specifying the number x of payload bytes employed for storing compressed or uncompressed data, bytes 4 through x+3 can be used for storing the compressed or uncompressed data, and the like.

According to an exemplary embodiment, an algorithm B for the profile B, or a template T1 based on the profile B, having an identification number associated therewith (for example, 1), can be employed to compress member expressions E down to 12 payload bytes (for example, x=12=4 bytes times three cmid values of the corresponding three expressions), and the like. The exemplary license L1 compressed into such an exemplary bit structure can be illustrated in an exemplary compressed byte table, as shown in Table 3.

TABLE 3 Exemplary Compressed Byte Table. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Hex 01 00 00 0C 00 00 00 7B 00 00 01 C8 00 00 00 18 Decimal 1 12 123 456 24 id x cmid 1 cmid 2 cmid 3

As shown in Table 3, for example, byte 0 can be used for storing the identification number 1 for the algorithm B for the profile B, or the template T1, bytes 1-3 can be used for storing the number x of payload bytes employed (x=12), and bytes 4 through 15 (x+3) can be used for storing the cmid values 123, 456, and 024 from the exemplary license L1.

According to an exemplary embodiment, an algorithm C for profile C, or a template T2 based on the profile C, having an identification number associated therewith (for example, 2) can be employed to compress any of its member expressions E down to 16 payload bytes (for example, x=14=4 bytes times four cmid values of the corresponding four expressions), and the like. The exemplary license L2 compressed into the exemplary bit structure can be illustrated in an exemplary compressed byte table, as shown in Table 4.

TABLE 4 Exemplary Compressed Byte Table. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Hex 02 00 00 10 00 00 00 7B 00 00 01 C8 00 00 03 15 00 00 00 18 Decimal 2 16 123 456 789 24 id x cmid 1 cmid 2 cmid 3 cmid 4

As shown in Table 4, for example, byte 0 can be used for storing the identification number 2 for the algorithm C for profile C, or the template T2, bytes 1-3 can be used for storing the number x of payload bytes employed (x=16), and bytes 4 through 19 (x+3) can be used for storing the cmid values 123, 456, 789, and 024 from the exemplary license L2.

Advantageously, the exemplary bit structure allows for the addition of additional compression algorithms, profiles, or templates, as devices employing the exemplary bit structure gain capabilities, as new algorithms, profiles, and templates are created, generated, derived, determined, and the like. In addition, the exemplary bit structure, advantageously, allows for the transmission and reception of uncompressed or raw data, for example, uncompressed or raw rights expressions.

The exemplary profile B or template T1, can include three variables that can be used to split the exemplary license L1 into four parts B1-B4, as illustrated in an exemplary profile or template table, as shown in Table 5.

TABLE 5 Exemplary Profile or Template. Resource String Name Value B1 <license>   <grant>    <cm:device cmid=“ B2     “/>    <cx:play/>    <cm:song cmid=“ B3     “/>   </grant>  <cm:issuerDevice>    <cm:device cmid=“ B4     “/>   </cm:issuerDevice> </license>

Advantageously, the parts B1-B4 can be stored as resource strings within a device, such as a resource-constrained device, to send and receive uncompressed or raw data, such uncompressed or raw rights expressions. A profile B device, such as a resource-constrained device, can receive a raw or uncompressed data string W, such as a raw or uncompressed rights expression string, corresponding to the exemplary profile B or template T1.

The profile B device can be configured to call, invoke, execute, and the like, a first exemplary function, as illustrated in Table 6 and in pseudo-code below. Advantageously, the first exemplary function can be employed to determine if the profile B device can play a song, and the like.

TABLE 6 First Exemplary Function. Item Name Description Function interpretXrML_B Determines if a profile B device can play a song. Input W The raw XrML. Input deviceId The device's id. Input songId The song's id. Output result ERROR 1, if the license is not in profile B. ERROR 2, if the device is incorrect. ERROR 3, if the song does not match. Otherwise, result is non-error representing the issuer device's id. It is the caller's responsibility to verify that the issuer device is trustworthy.

First Exemplary Function in Pseudo-Code with Uncompressed Date W:

Function interpretXrML_B(W, deviceId, songId) { Read through W comparing to B1 If mismatch before end of B1 then ERROR 1 Read integer from W into temp until reaching end of numbers If temp does not equal deviceId then ERROR 2 Read through W comparing to B2 If mismatch before end of B2 then ERROR 1 Read integer from W into temp until reaching end of numbers If temp does not equal songId then ERROR 3 Read through W comparing to B3 If mismatch before end of B3 then ERROR 1 Read integer from W into temp until reaching end of numbers Set result = temp Read through W comparing to B4 If mismatch before end of B4 then ERROR 1 Success. Return result }

Advantageously, the performance of the first exemplary function can be optimized, when operating on a compressed data string w, as illustrated below.

First Exemplary Function in Pseudo-Code with Compressed Data w:

Function interpretXrML_B(w, deviceId, songId) { algorithm = readBytes(w, 1); size = readBytes(w, 3); if(algorithm != 1 OR size != 12) { skipBytes(w, size); ERROR 1; } if(deviceId != readBytes(w, 4)) { skipBytes(w, 8); ERROR 2; } if(songId != readBytes(w, 4)) { skipBytes(w, 4); ERROR 3; } result = readBytes(w, 4); return result; }

The encoding of a rights expression, such as a license, can include converting the rights expression from a native form, such as XrML, into the template or profile counterpart of the license that can be employed on a resource-constrained device. An approach to perform such encoding can be referred to as explicit encoding, which typically works best when the original license can be almost identical to the template or profile counterpart of the license.

FIG. 3 illustrates an exemplary rights expression encoding and decoding sub-system 300 for resource-constrained devices in the Digital Rights Management system of FIG. 1. In the sub-system of FIG. 3, for example, high-end resources, such as an XrML parser, an XrML interpreter need not be employed for explicit encoding on a resource-constrained device. For example, a device 301 can receive an un-encoded license 303, and instead of parsing the license 303, for example, because of resource constraints, and the like, can employ an explicit encoder 305 to encode the license 303 into a form that the device 301 can later process, advantageously, without having to employ a general-purpose interpreter, and the like, but rather an interpreter 307, such as resource-constrained, or less than full-featured interpreter.

The template T1 or the profile B corresponding to the first exemplary license L1, as shown below, can be generated by removing parameters, values or data that are most likely to change from one instantiation of the exemplary license L1 to another, such as the values for the cmid variables.

Exemplary Template T1 or Profile B:

<license> <grant> <cm:device cmid=“”/> <cx:play/> <cm:song cmid=“”/> </grant> <cm:issuerDevice> <cm:device cmid=“”/> </cm:issuerDevice> </license>

The exemplary template T1 or profile B can be in the form an XrML-based template, profile, and the like. The exemplary template T1, or profile B, can be used, for example, to represent a license that can permit a particular device the right to play a particular song, that can reference a device that can issue the exemplary license L1, and the like.

The exemplary template T1, or profile B, can include the three variable elements that split the exemplary license L1 into the four parts B1-B4, as shown in Table 5. Advantageously, the parts B1-B4 can be stored as resource strings within the device 301 to enable the device 301 to send, and receive the un-encoded license 303, for example, raw or uncompressed rights expressions (W).

If the device 301 can receive a raw XrML string W, the device 301 can call the first exemplary function to determine if the device 301 can exercise a usage right specifying a manner of use, such as playing a song 309. In a similar manner, the device 301 can call a second exemplary function, as shown in Table 7 and in pseudo-code below, to generate an encoded license 311, such as the exemplary license L1. The first exemplary function can be included as part of the interpreter 307 functionality, and the second exemplary function can be included as part of the encoder 305 functionality.

TABLE 7 Second Exemplary Function. Item Name Description Function EncodeXrML_T1 Determines if a profile B device can encode a license. Input W The raw XrML. Input deviceId The device's id. Input songId The song's id. Output result ERROR 1, if the license is not a T1. Encoded T1.

Second Exemplary Function in Pseudo-Code:

Function EncodeXrML_T1(W,deviceId, songId) { Read through W comparing to B1 If mismatch before end of B1 then ERROR 1 Read integer from W into temp until reaching end of numbers Read through W comparing to B2 If mismatch before end of B2 then ERROR 1 Read integer from W into temp until reaching end of numbers Read through W comparing to B3 If mismatch before end of B3 then ERROR 1 Read integer from W into temp until reaching end of numbers Read through W comparing to B4 If mismatch before end of B4 then ERROR 1 Success. Return the variables from L1. }

If the exemplary license L1 can be in the profile B of the device 301, as described in T1, then the exemplary license L1 can be encoded by the encoder 305 in an encoded license table by the device 301, for example, as shown in Table 8, and the like.

TABLE 8 Exemplary Encoded License. 0 1 2 3 4 5 6 7 8 9 10 11 12 Hex 01 00 00 00 7B 00 00 01 C8 00 00 00 18 Decimal 1 123 456 24 id cmid 1 cmid 2 cmid 3

In Table 8, the corresponding 12-byte representation can be interpreted by the device 301, for example, to mean “use a template with identification number 1, fill in the first 3 variables with the values 123, 456, and 024” to generate the license 311. Advantageously, the encoded license 311, for example, corresponding to exemplary license L1, can be extremely compact, by only having to reference a template, or profile, and associated variables thereof, decreasing transmission costs, and storage costs of the exemplary license L1.

FIG. 4 is a flowchart illustrating the exemplary rights expression encoding and decoding process of FIG. 3. In FIG. 4, at step 401, for example, the encoding process can include obtaining a license. At step 403, for example, one or more values from variables fields of the license can be extracted until the employed values are removed from the license, as determined at step 405, to generate the template corresponding to the license. At step 407, for example, a template identifier can be assigned, and at step 409 the extracted values and the template identifier can be transmitted as the encoded license.

At step 411, for example, the decoding process can include receiving the template identifier along with the extracted values, and step 413 looking up a template corresponding to the template identifier, as determined at step 415. If no corresponding template can be found, step 417 can be employed to obtain a template corresponding to the template identifier, for example from an exemplary templatespace service, as later described. Once a template corresponding to the template identifier is obtained, at step 419 the received values can be inserted into the template corresponding to the template identifier to reconstruct the original license, advantageously, in a lossless manner.

The present invention includes recognition, for example, that not all licenses can be mapped explicitly into a template, or profile that a particular device, such as a slave device, can support. Advantageously, a trusted master device can interpret the license, find a mapping between the interpreted rights expressions and the set of templates that the slave device supports, and issue the resulting template to the slave device.

For example, FIG. 5 illustrates an exemplary rights expression template mapping sub-system 500 in the Digital Rights Management system of FIG. 1. In FIG. 5, for example, a license A (507) can grant the right to play a piece of content indefinitely within a specific home domain, such as the domain of a device A (505). However, a device B (501) can only support license template B (509), wherein device B (501) can play content between dates D1 to D2, such as given by the template B (509).

Typically, it would not be possible for device B (501), in this case the slave device, to interpret the license A (507), because the license A (507), for example, does not include the syntax, semantics of “playing between dates D1 and D2.” A user could employ another trusted device, such as the device A (505), in this case the master device, in the home domain for interpreting a wide variety of licenses, such as the license A (507). However, in further exemplary embodiment, the device A (505) can interact with the device B (501), for example, to get a list of templates that device B (501) supports, such as the template B (509), and the like.

In further exemplary embodiment, the device A (505) can establish a knowledge database including a list of templates that device B (501) can support, via other methods, such as configuration, and registration mechanisms. However, if the device A (505), for example, can be capable of interpreting the template B (509), and the license A (507), the device A (505) can issue a license B (503) to the device B (501), because a license based on template B (509) can be considered to include a subset of rights that can be issued in the license A (507). Advantageously, the license B (503) can be based on the template B (509), and can be explicitly encoded to generate a corresponding encoded license B (511) that the device B (501) can interpret. Accordingly, a general license, such as the license A (507), can be template mapped to devices, such as the device B (501), for example, which are resource-constrained by being able to interpret a limited amount of templates, or profiles.

Accordingly, FIG. 6 is a flowchart illustrating exemplary template mapping processes of the sub-system of FIG. 5. In FIG. 6, at step 601, for example, a domain license can be obtained granting a home domain, such as a home computer network, an unlimited right to play, view, render or execute, a piece of identified content, such as a music file, movie file, image file or software file. The user can then requests, for example, from a master device, such as a personal computer on the home network, that the content associated with the domain license be played on a resource-constrained device, such as an MP3 player.

According, at step 603, for example, the master device can query the slave device to determine the types of licenses, profiles, or templates that the slave device can support. At step 605, for example, the master device can determine that the slave device can not support the domain license, and, at step 607, for example, can retrieve a template corresponding to a license that the slave device can support, for example, from a template service, or from the slave device itself.

At step 609, for example, the master device can issue a license that the slave device can support, based on the retrieved template. Advantageously, the slave device need not be capable of interpreting the domain license, but rather can be capable of interpreting the license issued at step 609. Advantageously, the issued license can include a subset of the rights specified in the domain license.

At step 611, for example, the master device, the slave device, or another device, can be used to encode the license in any suitable manner, for example, as described with respect the exemplary embodiments. At step 613, the slave can receive a simple to interpret encoded license, which the slave can interpret at step 615 in any suitable manner, such as described with respect the exemplary embodiments.

Advantageously, the exemplary form of compression, and decompression of the described exemplary embodiments can be a considered lossless, allowing for the slave device to copy, reconstruct, regenerate, or duplicate the issued license from the encoded form thereof by replacing one or more of the values for the variables into a stored copy of the template, or profile. Thus, by employing an encoded license, an associated template, or profile, the encoding process can be reversed so that the original license, advantageously, can be reconstructed from the encoded form thereof.

The exemplary encoding, and decoding processes, advantageously, can be employed with digital signatures to validate, authenticate or ensure that an issued license has not been tampered with, hacked or compromised. For example, the value for a digital signature can be a variable employed with an encoded form of a license.

FIG. 7 further illustrates the exemplary rights expression encoding and decoding sub-system FIG. 3, based on such a license signature value 705. In FIG. 7, for example, a signature value 705 can be employed along with one or more values 701-703, as values for variables corresponding to a template or profile that can be extracted from a license 707, such the exemplary license L11.

Advantageously, the license 707 can be encoded by transmitting the values 701-703 in the form of an encoded license 709 that can be delivered, to example, to a resource-constrained device. The values 701-703 can be used to populate the corresponding variables in a stored copy of a template, or profile to generate a decoded license 711. Advantageously, the signature value 705 can be restored into the corresponding variable fields of the corresponding template, profile, and the like, signature validation, authentication, and the like, techniques can be employed with the decoded license 711, such as according to the described exemplary embodiments, and the like.

The exemplary signature technique, advantageously, can employed with a resource-constrained device that can encode the license 709, but may lack facilities, sign, or re-sign the encoded license 709, for example, because such device may not be part of a trust domain, or may not have sophisticated processing capabilities. In a further exemplary embodiment, however, an encoded form of a license can be signed, for example, using any suitable digital signature technique, such as according to the described exemplary embodiments.

For example, FIG. 8 further illustrates the exemplary rights expression encoding and decoding sub-system FIG. 3 based on a signature value 805 for license variables 801-803. In FIG. 8, for example, if a device that can perform the exemplary encoding processes can be part of a trust domain, such a device convert an original license 807 to the encoded form 809, sign the encoded form of the license 809, and transmit the signature value 805 along with the variables 801-803.

Advantageously, the signature value 805 can be employed to validate, authenticate, or ensure that the variables 801-803 are not tampered with, hacked, or compromised. Thus, the integrity, and validity of template identifiers, profile identifiers, and values for variables that can correspond to a template, or profile can be ensured, and trusted.

Based on which of the exemplary signature approaches can be employed, the signature value can used validate encoded or decoded forms of a license. In addition, the exemplary template mapping can occur during interpretation, by employing templates as a profiling technique, and a rights language interpreter employed need not be a feature-rich language parser, or interpreter. For example, the interpretation of the meaning of a license can occur, be predetermined, pre-built, or pre-designed in the corresponding device, such as a resource-constrained.

Thus, advantageously, when a device receives a license, the device can integrate a meaning of the license, along with the variables included in the license. For example, an encoded template or profile, advantageously, can be interpreted, based on the following pseudo-code fragment:

Function interpretXrML_B(w, songId) { TemplateNumber=Readbytes (w, 1) LicDeviceID=Readbytes (w, 4) LicSongID=Readbytes (w, 4) if(TemplateNumber!= 1) { return(NO_PERMISSION_PLAY) } if(LicDeviceID!= THISDEVICEID) { return(NO_PERMISSION_PLAY) } if(lLicSongID!= songID) { return(NO_PERMISSION_PLAY) } return (YES_PERMISSION_PLAY)

Advantageously, such an exemplary form of interpretation can rely on a developer to match an understanding of what can be described in a template, or profile to whatever functions a device can carry out. Accordingly, a rights language can be employed as a common point of understanding between a resource-constrained device that can understand its templates or profiles, a developer of such a device, a license issuer, and an encoding device, which can be mapping licenses to the predetermined templates or profiles.

Other exemplary technologies can be provided, advantageously, to supplement or enhance the exemplary template mapping or profiling, and to facilitate effective managed content distribution to resource-constrained devices. An exemplary templatespace can be employed to allow a license encoded via the exemplary template mapping to specify which template can be associated therewith.

For example, if an encoded license simply specifies “use template 1,” the meaning of “template 1” can be ambiguous. Advantageously, the exemplary templatespace can be a namespace that provides context for the integer “1” in the noted expression. In this way, instead of simply encoding the license with a series, such as “1,” “123,” “456,” “24,” as shown in Table 8, where “1” can be the template identifier, and “123,” “456,” and “024” can be the values for the variables, the license can be encoded as “Acme.1,” “123,” “456,” “024.”

Advantageously, Acme.1 can reference a namespace from which “1” could derive concise meaning. For example, Acme Corporation could create a series of well-defined products that its product line would support. A device that would receive the templatespace-encoded license, for example, could then identify the appropriate template by accessing a database associated with “Acme” and then the device could index into the database via the integer 1.

The exemplary templatespaces, thus, advantageously, allow templates to be retrieved, stored, managed and accessed, in an unambiguous and scalable fashion. Exemplary templatespaces could thus include: Acme Inc., Acme Cameras, Acme PVR Model 123, bios version 1.3, Personal Video Recorder Makers of Europe, acmetemplates.com, and the like. Advantageously, as makers of resource-constrained devices adopt content that can be distributed with a rights language, standardized sets of templates that are viable for respective product spaces can be deployed.

Templatespaces themselves may not fully address the issue of template lifecycles. Advantageously, however, templatespace services can be deployed. For example, a templatespace service can include a service that manages the templates themselves, so that the templates can be retrieved later by devices that are performing the exemplary template mapping, and by systems that wish to decode a license back to an original form thereof. The templatespace service can also provide other functions, such as query for templates offered by a given company, support for revisions and updates to the templates and/or mapping thereof to licenses.

Advantageously, a templatespace service can be deployed, via a number of methodologies, for example, including a computer network based service, such as a website, a service built into a resource-constrained device, and the like. For example, FIG. 9 illustrates an exemplary templatespace service 900 that can be deployed via a number of methodologies, for example, including a computer network-based service, such as a website or a service built into a resource-constrained device.

In FIG. 9, a user can acquire content bound by a rich rights language on master device 901, such as a personal computer, via a license source 903. The user can receive as an update from a device manufacturer 905, a new bios, for a slave device 907, such as a handheld mobile mp3 player, that allows the user to properly treat the content with a new license template, such as a “play only during date a-b” type of template of the exemplary embodiments. For example, the new bios could support a number of new templates on the slave device 907.

The device manufacturer can make templates available via a template service 909, such as a publicly accessible network service, and the like. When the user moves the content to the slave device 907, based on information from the slave device 907, the master device 901 can acquire a list of templates supported by the slave device 907 from the template service 909. The master device 901 can interpret the rights language from the templatespace network service 909, and determine that the new template supported can be appropriate for transferring the content from the master device 901 to the slave device 907. The master device 901 then can encode and issue a new license to the slave device 907 based on the exemplary license encoding techniques.

In a further exemplary embodiment, a similar flow and rights lifecycle can be accomplished, but instead, wherein the manufacturer 905 makes the templates available on the slave device 907 itself. In addition, legacy devices or devices that have little or no support for DRM can employ an industry-created generic template that describes the behavior of such device. Advantageously, the legacy device would not receive a rights language of any form, but rather would treat content the same regardless of the source.

For example, a digital television can employ a standard rights template created to represents “digital televisions.” Manufactures of digital televisions then could agree to the terms expressed in such a template and develop products that constrain their content usage rules to such a template. Advantageously, a master device can interpret a license and control content delivery to such device only when the usage rights can be granted.

In an exemplary embodiment, a symbolic representation can be employed to encode, and the like, a rights expression, in a form or a template or profile, for example, as shown in Tables 3, 5, and 8. A symbolic representation can include a graphical representation based on glyphs, a modulated or varied signal-based representation, such as based on modulated or varied light or sound signals. Thus, the symbolic representation of a template or profile can be encoded, derived, and the like, based on glyph structures, such star-shaped structures, square-shaped structures, rectangular-shaped structures, circular-shaped structures, triangular-shaped structures or portions thereof, and the like. In a similar manner, a template or profile can be encoded, derived, and the like, based on modulated or varied signals, lights, sounds, series of sounds, light pulses, using at any suitable frequency, amplitude, including ultraviolet waves, x-rays, microwaves, radio waves, employing lasers, modulated or convoluted information, different colors or wavelengths, and electric or magnetic field variations.

For example, FIG. 10 illustrates an exemplary symbolic representation of the templates or profiles corresponding to Tables 3, 5, or 8. In FIG. 10, for example, an exemplary symbolic representation can be derived from a glyph structure, for example, based on a star-shaped structure, and the like, and can be used for expressing the templates or profiles corresponding to Tables 3, 5, or 8. In an exemplary embodiment, the symbols 1001-1004 derived from the star-shaped structure can be taken from the Red, Green, and Blue (RGB) color space. Thus, the symbols 1001-1004 of the star-shaped structure can include the Red (R), Green (G), and/or Blue (B) colors. Accordingly, in a basic case, wherein no colors can be combined, 12 symbols can be generated (for example, four symbols times three colors). To increase the number of members or symbols, however, complex symbols 1011-1019 having overlapping colors can be generated, as shown in FIG. 10.

Thus, two or more symbols of different colors, for example, up to all 12 symbols, can be combined so as to overlap on a physical location, to potentially produce part or all of the star-shaped structure in different colors or combination of colors for each part of the star shape. For example, the color of the resulting horizontal symbol 1001 of the complex symbol 1011 can be based on the combination of Green and Red symbols 1001. In this way, the symbols 1001-1004, in various color combinations, can be used to generate the complex symbols 1011-1019, as shown in FIG. 10.

Accordingly, the number of complex symbols in the exemplary symbol set illustrated by FIG. 10, for example, can be (2¹²−1) or 4095 symbols, assuming that a blank space is not considered a symbol. Advantageously, with the numerous choices for the complex symbols provided by the exemplary embodiment, correspondingly complex and comprehensive symbolic representations of information, such as information for grammar, language, and the like, for a rights expressions can be generated.

For example, as shown in FIG. 10, the exemplary rights expression 1021 can indicate the templates or profiles corresponding to Tables 3, 5, or 8. In FIG. 10, for example, the symbols 1011-1019 can be used to express the template or profile identification “1” followed the first cmid value “123” of the template or the number of pay load bytes “x” of the profile; followed by the second cmid value “456” of the template or the first cmid value “123” of the profile; followed by the third and final cmid value “024” of the template or the second cmid value “456” of the profile; followed by the third and final cmid “024” of the profile. In this manner, symbols can be generated and transmitted so as to represent templates or profiles corresponding to Tables 3, 5, or 8.

In an exemplary embodiment, the glyphs, symbols, words, messages, and the like, of the exemplary embodiments used to convey information, for example, about a rights expression, can be encoded using light, sound, a series of sounds, light pulses, and the like, using at any suitable frequency, amplitude, and the like, can include ultraviolet waves, x-rays, microwaves, radio waves, and the like, can employ lasers, modulated or convoluted information, different colors or wavelengths, electric or magnetic field variations, and the like.

In an exemplary embodiment, any suitable series of the glyphs, symbols, words, messages, and the like, of the exemplary embodiments employed can have its own grammar, rules, and the like, which provide a meaning to a transmitted message. For example, a sound or light in a range of frequencies that a human ear or eye cannot detect, can be employed for transmitting the glyphs, symbols, words, messages, and the like, of the exemplary embodiments, during security applications, privacy applications, and the like. In this way, a transmitted message can be made transparent to a user or users, but at the same can be retrieved, understood, and the like, by a suitable sensor, detector, and the like. In an exemplary embodiment, the glyphs, symbols, words, messages, and the like, of the exemplary embodiments can be expressed using any suitable human or machine sensing organ or device, and the like, so long as that the sensed information, message, and the like, can be quantized, digitized, expressed, and the like, based on numbers, bits, bytes, and the like.

The devices and subsystems of the Digital Rights Management system 100, for example, as described with respect to FIGS. 1-10, can communicate, for example, over a communications network 170, and can include, for example, any suitable servers, workstations, personal computers (PCs), laptop computers, PDAs, Internet appliances, set top boxes, modems, handheld devices, telephones, cellular telephones, wireless devices, other devices, and the like, capable of performing the processes of the disclosed exemplary embodiments. The devices and subsystems of the Digital Rights Management system 100, for example, can communicate with each other using any suitable protocol and can be implemented using a general purpose computer system. One or more interface mechanisms can be used in the Digital Rights Management system 100 including, for example, Internet access, telecommunications in any suitable form, such as voice, modem, and the like, wireless communications media, and the like. Accordingly, communications network 170 can include, for example, wireless communications networks, cellular communications networks, satellite communications networks, Public Switched Telephone Networks (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, hybrid communications networks, combinations thereof, and the like. In addition, the communications network 170 can be the same or different networks.

As noted above, it is to be understood that the Digital Rights Management system 100, for example, as described with respect to FIGS. 1-10, is for exemplary purposes, as many variations of the specific hardware used to implement the disclosed exemplary embodiments are possible. For example, the functionality of the devices and the subsystems of the Digital Rights Management system 100 can be implemented via one or more programmed computer systems or devices. To implement such variations as well as other variations, a single computer system can be programmed to perform the special purpose functions of one or more of the devices and subsystems of the Digital Rights Management system 100. On the other hand, two or more programmed computer systems or devices can be substituted for any one of the devices and subsystems of the Digital Rights Management system 100. Accordingly, principles and advantages of distributed processing, such as redundancy, replication, and the like, also can be implemented, as desired, for example, to increase the robustness and performance of the Digital Rights Management system 100.

The Digital Rights Management system 100, for example, as described with respect to FIGS. 1-10, can be used to store information relating to various processes described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like, of the devices and sub-systems of Digital Rights Management system 100. One or more databases of the devices and subsystems of the Digital Rights Management system 100 can store the information used to implement the exemplary embodiments. The databases can be organized using data structures, such as records, tables, arrays, fields, graphs, trees, lists, and the like, included in one or more memories, such as the memories listed above.

All or a portion of the Digital Rights Management system 100, for example, as described with respect to FIGS. 1-10, can be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, micro-controllers, and the like, programmed according to the teachings of the disclosed exemplary embodiments. Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the disclosed exemplary embodiments. In addition, the Digital Rights Management system 100 can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of component circuits.

Advantageously, the exemplary embodiments described herein can be employed in offline systems, online systems, and the like, and in applications, such as TV applications, computer applications, DVD applications, VCR applications, appliance applications, CD player applications, and the like. In addition, the signals employed to transmit the glyphs, symbols, words, messages, profiles, templates, and the like, of the exemplary embodiments, can be configured to be transmitted within the visible spectrum of a human, within the audible spectrum of a human, not within the visible spectrum of a human, not within the audible spectrum of a human, combinations thereof, and the like.

Although the exemplary embodiments are described in terms of items, such as music files, audio files, and the like, the exemplary embodiments are applicable to any suitable items, such as digital content, devices, software, services, goods, resources, and the like, and can be practiced with variations in technology, interface, language, grammar, content, rights, offerings, services, speed, size, limitations, devices, and the like.

While the present invention have been described in connection with a number of embodiments and implementations, the present invention is not so limited but rather covers various modifications and equivalent arrangements, which fall within the purview of the appended claims.

APPENDIX Sample Extension Schema (schema/2001/11/compactMusic): <?xml version=“1.0” encoding=“UTF-8”?> <!-- Copyright (C) 2001 ContentGuard Holdings, Inc. All rights reserved. “ContentGuard” is a registered trademark and “XrML”, “eXtensible rights Markup Language”, the XrML logo and the ContentGuard logo are trademarks of ContentGuard Holdings, Inc. All other trademarks are properties of their respective owners. --> <!-- NOTE: This is an example extension schema. It is not part of XrML 2.0 Specification. -- > <xsd:schema targetNamespace=“http://www.xrml.org/schema/2001/11/compactMusic” xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns:sx=“http://www.xrml.org/schema/2001/11/xrml2sx” xmlns:r=“http://www.xrml.org/schema/2001/11/xrml2core” xmlns:cx=“http://www.xrml.org/schema/2001/11/xrml2cx” xmlns:cm=“http://www.xrml.org/schema/2001/11/compactMusic” elementFormDefault=“qualified” attributeFormDefault=“unqualified”>  <xsd: import namespace=“http://www.xrml.org/schema/2001/11/xrml2cx” schemaLocation=“xrml2cx.xsd”/>  <!-- - Principals-->  <xsd:element name=“device” substitutionGroup=“r:principal”>   <xsd:complexType>    <xsd:complexContent>     <xsd:extension base=“r:Principal”>      <xsd:attribute name=“cmid” type=“xsd:int” use=“optional”/>     </xsd:extension>    </xsd:complexContent>   </xsd:complexType>  </xsd:element>  <!-- - Resources-->  <xsd:element name=“song” substitutionGroup=“r:resource”>   <xsd:complexType>    <xsd:complexContent>     <xsd:extension base=“r:Resource”>      <xsd:attribute name=“cmid” type=“xsd:int” use=“optional”/>     </xsd:extension>    </xsd:complexContent>   </xsd:complexType>  </xsd:element>  <!-- - Property Resources-->  <xsd:element name=“myDomain” substitutionGroup=“r:resource”>   <xsd:complexType>    <xsd:complexContent>     <xsd: extension base=“r:Resource”/>    </xsd:complexContent>   </xsd:complexType>  </xsd:element>  <!-- - Conditions-->  <xsd:element name=“copyManagement” type=“sx:StatefulCondition” substitutionGroup=“r:condition”/>  <!-- - Issuer Descriptions-->  <xsd:element name=“issuerDevice”>   <xsd:complexType>    <xsd:complexContent>     <xsd:extension base=“cm:IssuerRaw”>      <xsd:sequence minOccurs=“0”>       <xsd:element ref=“cm:device”/>      </xsd:sequence>     </xsd:extension>    </xsd:complexContent>   </xsd:complexType>  </xsd:element>  <xsd:complexType name=“IssuerRaw”>   <xsd:complexContent>    <xsd: restriction base=“r:Issuer”/>   </xsd:complexContent>  </xsd:complexType>  <!-- - Service Descriptions-->  <xsd:element name=“copyKeeper” type=“cm:StateOnDevice” substitutionGroup=“r:licensePart”/>  <xsd:element name=“countKeeper” type=“cm:StateOnDevice” substitutionGroup=“r:licensePart”/>  <xsd:element name=“intervalKeeper” type=“cm:StateOnDevice” substitutionGroup=“r:licensePart”/>  <xsd:complexType name=“StateOnDevice”>   <xsd:complexContent>    <xsd:extension base=“r:LicensePart”>     <xsd:sequence minOccurs=“0”>      <xsd:element ref=“cm:device”/>     </xsd:sequence>     <xsd:attribute name=“key” type=“xsd:int” use=“optional”/>    </xsd:extension>   </xsd:complexContent>  </xsd:complexType> </xsd:schema> 

1. A method for encoding and transmitting a rights expression for association with an item for use in a system for controlling use of the item in accordance with the rights expression, said method comprising: specifying rights expression information indicating a manner of use of an item, said rights expression information including at least one element, said element having a variable and corresponding value for said variable; performing an encoding process, including: identifying a rights expression template which maps to said rights expression information, determining an identifier associated with said rights expression template that maps to said rights expression information, extracting from said rights expression information said value corresponding to said variable corresponding to said element to populate said rights expression template, and encoding a license adapted to be enforced on a device based on said variable and said identifier, said license including an identification of said template and said value for said variable, transmitting said encoded license to the device; interpreting said encoded license based on said identification of said template and said value for said variable; and enforcing said manner of use of said item based upon said interpretation of said encoded license.
 2. The method as recited in claim 1, wherein said rights expression information includes conditions that must be satisfied in order to exercise a manner of use of said item on said device.
 3. The method as recited in claim 1, further comprising: interpreting said encoded license on said device based on said identification of said template and said value for said variable.
 4. The method as recited in claim 3, wherein said rights expression information includes a digital signature thereof, and said method further comprises: extracting from said rights expression information said digital signature; including in said encoded license said digital signature; reconstructing said rights expression information from said encoded license; and verifying said digital signature before enforcing said encoded license on said device.
 5. The method as recited in claim 1, wherein said template comprises a data structure.
 6. The method as recited in claim 1, wherein said template is associated with a company.
 7. The method as recited in claim 1, wherein said template is associated with a type of device.
 8. The method as recited in claim 1, wherein said device comprises a handheld device.
 9. The method as recited in claim 1, wherein said device comprises a resource constrained device.
 10. The method as recited in claim 1, further comprising: encoding a sub-license that is a subset of said encoded license and is adapted to be enforced on another device based on said encoded license and a template associated with said another device.
 11. The method as recited in claim 10, wherein said template associated with said another device is retrieved from a template server.
 12. The method as recited in claim 1, further comprising: digitally signing said encoded license; associating said encoded license with the digital signature; and verifying said digital signature before enforcing said encoded license on said device.
 13. The method as recited in claim 1, wherein said device comprises a rendering device.
 14. The method as recited in claim 1, wherein said rights expression information is grammar-based.
 15. The method as recited in claim 1, wherein said template is associated with another device and is retrieved from a template server.
 16. The method as recited in claim 1, wherein at least one of said rights expression information, and said template comprises a glyph.
 17. The method of claim 1, further comprising: identifying at least one rights expression template a device can support; and interpreting said rights expression information to determine whether or not the use of a particular rights expression template in the device would violate said rights expression information.
 18. The method of claim 17, further comprising transmitting the particular rights expression template and a variable associated with the rights expression template to the device if the use of the particular rights expression template in the device would not violate the rights expression information.
 19. The method of claim 1, further comprising transmitting said encoded license and said rights expression information to the device.
 20. The method of claim 1, further comprising verifying, after the license has been encoded, a signature that was applied to the unencoded license using a copy of the unencoded license.
 21. The method of claim 1, further comprising storing, in an independent database, a further rights expression template that can be transmitted to the device if the device is not able to interpret the encoded license.
 22. The method of claim 1, further comprising managing publications of templates to a service which identifies which devices support what templates and provides information to the device including at least one of an identification of a compatible rights expression template, a supported version of a compatible rights expression template, and information regarding one or more revisions of the device.
 23. The method of claim 22, further comprising: discovering at least one rights expression template that is supported by the device; retrieving an unencoded version of the discovered rights expression template; and evaluating how to communicate with the device based on the discovered rights expression template.
 24. A system for encoding and transmitting a rights expression for association with an item for use in a system for controlling use of the item in accordance with the rights expression, said system comprising: means for specifying rights expression information indicating a manner of use of an item, said rights expression information including at least one element, said element having a variable and corresponding value for said variable; means for performing an encoding process, including: means for identifying a rights expression template which maps to said rights expression information, means for determining an identifier associated with said rights expression template that maps to said rights expression information, means for extracting from said rights expression information said value corresponding to said variable corresponding to said element to populate said rights expression template, and means for encoding a license adapted to be enforced on a device based on said variable and said identifier, said license including an identification of said template and said value for said variable, means for transmitting said encoded license to the device; means for interpreting said encoded license based on said identification of said template and said value for said variable; and means for enforcing said manner of use of said item based upon said interpretation of said encoded license.
 25. The system as recited in claim 24, wherein said rights expression information includes conditions that must be satisfied in order to exercise a manner of use of said item on said device.
 26. The system as recited in claim 24, further comprising: means for interpreting said encoded license on said device based on said identification of said template and said value for said variable.
 27. The system as recited in claim 26, wherein said rights expression information includes a digital signature thereof, and said system further comprises: means for extracting from said rights expression information said digital signature; means for including in said encoded license said digital signature; means for reconstructing said rights expression information from said encoded license; and means for verifying said digital signature before enforcing said encoded license on said device.
 28. The system as recited in claim 24, wherein said template comprises a data structure.
 29. The system as recited in claim 24, wherein said template is associated with a company.
 30. The system as recited in claim 24, wherein said template is associated with a type of device.
 31. The system as recited in claim 24, wherein said device comprises a handheld device.
 32. The system as recited in claim 24, wherein said device comprises a resource constrained device.
 33. The system as recited in claim 24, further comprising: means for encoding a sub-license that is a subset of said encoded license and is adapted to be enforced on another device based on said encoded license and a template associated with said another device.
 34. The system as recited in claim 33, wherein said template associated with said another device is retrieved from a template server.
 35. The system as recited in claim 24, further comprising: means for digitally signing said encoded license; means for associating said encoded license with the digital signature; and means for verifying said digital signature before enforcing said encoded license on said device.
 36. The system as recited in claim 24, wherein said device comprises a rendering device.
 37. The system as recited in claim 24, wherein said rights expression information is grammar-based.
 38. The system as recited in claim 24, wherein said template is associated with another device and is retrieved from a template server.
 39. The system as recited in claim 24, wherein at least one of said rights expression information, and said template comprises a glyph.
 40. The system as recited in claim 24, wherein said means for specifying, said means for performing, said means for extracting and said means for encoding comprise devices of a computer system.
 41. The system as recited in claim 24, wherein said means for specifying, said means for performing, said means for extracting and said means for encoding comprise computer readable instructions recorded on a medium.
 42. The system of claim 24, further comprising: means for identifying at least one rights expression template a device can support; and means for interpreting said rights expression information to determine whether or not the use of a particular rights expression template in the device would violate said rights expression information.
 43. The system of claim 42, further comprising means for transmitting the particular rights expression template and a variable associated with the rights expression template to the device if the use of the particular rights expression template in the device would not violate the rights expression information.
 44. The system of claim 24, further comprising means for transmitting said encoded license and said rights expression information to the device.
 45. The system of claim 24, further comprising means for verifying, after the license has been encoded, a signature that was applied to the unencoded license using a copy of the unencoded license.
 46. The system of claim 24, further comprising means for storing, in an independent database, a further rights expression template that can be transmitted to the device if the device is not able to interpret the encoded license.
 47. The system of claim 24, further comprising means for managing publications of templates to a service which identifies which devices support what templates and provides information to the device including at least one of an identification of a compatible rights expression template, a supported version of a compatible rights expression template, and information regarding one or more revisions of the device.
 48. The system of claim 47, further comprising: means for discovering at least one rights expression template that is supported by the device; means for retrieving an unencoded version of the discovered rights expression template; and means for evaluating how to communicate with the device based on the discovered rights expression template. 